I have a module with multiple baselines. The current baseline has gone through major changes and reorganization (literally requirements moving around). Unfortunately, it turns out that the previous baseline (let's call it A) is going to have to have changes made to it, while the currently baseline (let's call it B) will go forward. So we have overlapping baselines. I've made a copy of the module so have B alone in a module with the correct requirement IDs. I'm fine with having separate modules at this point, but I can't figure out a way to delete the current module B from the old module so that I can access A and move that forward. I've tried deleting the B baseline, but still it shows the contents of B as the current baseline. Please tell me there is some workaround!! AmyAybar - Thu Apr 25 11:45:03 EDT 2013 |
Re: Baseline help Hi Amy You can copy the A baseline to create a new formal module, but the Object Identifier will be reassigned in it. (File->Baseline->Copy) Any links will also be lost. As you already learned, Doors does not permit branching or merging. It keeps track of any changes you make, but it will not allow you to easily rollback any changes to get to a previous version. The best you can do is roll back the current version to the last baseline, and that would take some effort too. |
Re: Baseline help You can also read this post. |
Re: Baseline help BranchManager for DOORS is a Ready for IBM Rational software product that allows branching and merging. https://www-304.ibm.com/partnerworld/gsd/w3solutiondetails.do?solutionId=49140&lc=en&state=P
|